home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group97a.txt
/
000019_icon-group-sender _Tue Jan 21 09:26:56 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Received: by cheltenham.cs.arizona.edu; Wed, 22 Jan 1997 08:48:48 MST
Date: Tue, 21 Jan 1997 09:26:56 -0600
Message-Id: <199701211526.JAA31871@ns1.cmpu.net>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: gep2@computek.net
Subject: Re: y2k
To: icon-group@cs.arizona.edu
X-Mailer: SPRY Mail Version: 04.00.06.17
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 907
>> Umm, Icon IS y2k safe, right?
>I don't use Icon, but I've been always interested in it but never got
enough time.
That's probably precisely why you NEED to take time to learn it. :-) It ought
to SAVE you more time by using it than it TAKES you to learn it.
>But I wonder what does the y2k problem has to do with Icon? IMHO
all prog. languages are y2k safe.
Not necessarily... there are a number of y2k issues, not just at the programming
language level.
1) I suspect that some PC BIOSes aren't even y2k safe.
2) I suspect that some versions of MS-DOS aren't y2k safe (and many of the
MS-DOS command utilities probably aren't, either).
3) Many languages have runtimes with functions which return the "year" as a
two-digit number and/or don't generate the high-order two ASCII digits correctly
for the year after 1999 (etc.)
Gordon Peterson
http://www.computek.net/public/gep2/